fetcher: Drop max queue size assertion in libsoup/libcurl backends
authorColin Walters <walters@verbum.org>
Wed, 14 Feb 2018 20:28:17 +0000 (15:28 -0500)
committerAtomic Bot <atomic-devel@projectatomic.io>
Wed, 14 Feb 2018 23:15:09 +0000 (23:15 +0000)
commit96eec98f39054f3c1dfc6cda7e43c853157ca110
treefdb7785a96c458195aaf1612516eb00ed5f48353
parent8dd68fb9f9c0cdc8fb8090eebd06265836e55bfc
fetcher: Drop max queue size assertion in libsoup/libcurl backends

Since f4d1334e19ce3ab2f8872b1e28da52044f559401 the primary pull code maintains a
maximum queue. In that commit message I said `Note that I kept an assertion.`.
But I think this is wrong since while it covers a lot of the normal cases, if
one is e.g. trying to fetch a ton of refs, the primary pull code doesn't yet
queue those.  While it'd be nice to queue those, it isn't worth carrying
extra assertions in the backends that can still trigger.

Closes: https://github.com/ostreedev/ostree/issues/1451
Closes: #1453
Approved by: dbnicholson
src/libostree/ostree-fetcher-curl.c
src/libostree/ostree-fetcher-soup.c